This forum is closed to new posts and
responses. The content has been migrated to the Digital Solutions Community. Please join us there for new content as well as this content. For customer support, please visit the official HCL customer support channels below:
the domlog is already enabled, and we're tracking every request (including log-ins/log-outs), so we can create a view that only includes log-in requests and query that. As you can imagine, that makes our domlog get pretty big after awhile, so we purge old log entries (>4 months old). Some of our users are dormant for 6 months or more so when they do log in, the last login info from the domlog would be purged. So it sounds like with your suggestion we would need to have a syncing agent that grabs the last log-in info in the domlog and copies it over to another database. And since this information would need to real time, we would need to query both the new domlog.nsf view and the other place-holder DB.
Am I over-complicating this? Or is this more or less what you're suggesting?
O, and thanks for your help.
Feedback response number WEBB99YRNZ created by ~Umberto Frojumitexlen on 07/26/2013